chore: update build process to use ng-packgr builder#46
Merged
NathanWalker merged 1 commit intoNativeScript:fix/ng13-routingfrom Dec 21, 2021
Merged
Conversation
wSedlacek
force-pushed
the
chore/update-build-process
branch
from
f750eed to
7e98511
Compare
NathanWalker
changed the base branch from
feat/angular13
to
fix/ng13-routing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
What is the current behavior?
The build process was previously using a custom script.
What is the new behavior?
With advancements in the ng-packgr the custom build script is no longer necessary and all processes it was doing can be left to the ng-packgr executor.
With using the executor it makes the build no longer include the es2015 bundles which were removed from the recommended Angular Package Format with the release of Angular 13